GraphRAG performance enhacements #924
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Rita Brugarolas <[email protected]>
for more information, see https://pre-commit.ci
…o directly run build communities Signed-off-by: Rita Brugarolas <[email protected]>
for more information, see https://pre-commit.ci
Signed-off-by: Rita Brugarolas <[email protected]>
Signed-off-by: Rita Brugarolas <[email protected]>
for more information, see https://pre-commit.ci
Signed-off-by: Rita Brugarolas <[email protected]>
Signed-off-by: rbrygaro <[email protected]>
for more information, see https://pre-commit.ci
|
There are lot of dataprep backends and neoj4/llama is not the default one used in docker compose files and Helm charts. Do the ones used by default have also similar bottleneck? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: When property graph store gets filled (~12K nodes, 15K relationships) insertion time in dataprep gets slow.
Extraction + insertion starts at ~30 sec and once it gets filled grows to (~12K nodes, 15K relationships) ~800 sec
Perf bottleneck this cypher call in llama-index to do node upsert:
https://github.com/run-llama/llama_index/blob/795bebc2bad31db51b854a5c062bedca42397630/llama-index-integrations/graph_stores/llama-index-graph-stores-neo4j/llama_index/graph_stores/neo4j/neo4j_property_graph.py#L334
WIP solution: